Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarLint
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarCloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube

Secrets
ABAP
Ansible
Apex
AzureResourceManager
C
C#
C++
CloudFormation
COBOL
CSS
Dart
Docker
Flex
Go
HTML
Java
JavaScript
JCL
Kotlin
Kubernetes
Objective C
PHP
PL/I
PL/SQL
Python
RPG
Ruby
Scala
Swift
Terraform
Text
TypeScript
T-SQL
VB.NET
VB6
XML

HTML static code analysis

Unique rules to find Bugs, Security Hotspots, and Code Smells in your HTML code

Tags

Impact

Clean code attribute

Heading elements should have accessible content
Code Smell
Anchor tags should not be used as buttons
Code Smell
Interactive DOM elements should not have non-interactive ARIA roles
Code Smell
Non-interactive DOM elements should not have interactive ARIA roles
Code Smell
"tabIndex" values should be 0 or -1
Code Smell
DOM elements should use the "autocomplete" attribute correctly
Code Smell
Focusable elements should not have "aria-hidden" attribute
Code Smell
ARIA properties in DOM elements should have valid values
Code Smell
HTML "<table>" should not be used for layout purposes
Code Smell
"aria-label" or "aria-labelledby" attributes should be used to differentiate similar elements
Code Smell
Videos should have subtitles
Code Smell
Attributes deprecated in HTML5 should not be used
Code Smell
Sections of code should not be commented out
Code Smell
Track uses of "FIXME" tags
Code Smell
Meta tags should not be used to refresh or redirect
Code Smell
Links should not directly target images
Code Smell
Label elements should have a text label and an associated control
Code Smell
Elements with an interactive role should support focus
Code Smell
Images should have a non-redundant alternate description
Code Smell
Non-interactive DOM elements should not have an interactive handler
Code Smell
Non-interactive elements shouldn't have event handlers
Code Smell
DOM elements should not use the "accesskey" property
Code Smell
Non-interactive DOM elements should not have the `tabIndex` property
Code Smell
Anchors should contain accessible content
Code Smell
DOM elements with the `aria-activedescendant` property should be accessible via the tab key
Code Smell
"<object>" tags should provide an alternative content
Code Smell
Image, area and button with image elements should have an "alt" attribute
Code Smell
Track uses of "TODO" tags
Code Smell
Some Java packages or classes should not be used in JSP files
Code Smell
Disallowed "taglibs" should not be used
Code Smell
Track lack of copyright and license headers
Code Smell
Dynamic includes should not be used
Code Smell
Track uses of disallowed elements
Code Smell
The "style" attribute should not be used
Code Smell
Track uses of disallowed attributes
Code Smell
Track lack of required child elements
Code Smell
Track uses of disallowed child elements
Code Smell
Track lack of required attributes
Code Smell
Track lack of required parent elements
Code Smell
Files should not be too complex
Code Smell
Web pages should not contain absolute URIs
Code Smell
JSP expressions should not be used
Code Smell
JavaScript scriptlets should not have too many lines of code
Code Smell
Track lack of required an element with the required "id"
Code Smell
Track uses of disallowed namespaces in XHTML documents
Code Smell
Links with identical texts should have identical targets
Code Smell
Favicons should be used in all pages
Code Smell
Links should not target "#" or "javascript:void(0)"
Code Smell
Files should not have too many lines
Code Smell
Lines should not be too long
Code Smell
Multiple "page" directives should not be used
Code Smell
White space should be used in JSP/JSF tags
Code Smell
HTML comments should be removed
Code Smell
Attributes should be quoted using double quotes rather than single ones
Code Smell
Heading tags should be used consecutively from "H1" to "H6"
Code Smell
Tabulation characters should not be used
Code Smell
Track presence of forbidden parent element
Code Smell

Videos should have subtitles

intentionality - complete

maintainability

Code Smell

MajorSonarSource default severity
click to learn more

accessibility
html5

Why is this an issue?

In order to make your site usable by as many people as possible, subtitles should be provided for videos.

This rule raises an issue when a video does not include at least one <track/> tag with the kind attribute set to captions, or descriptions or at the very least subtitles.

Note that the subtitles kind is not meant for accessibility but for translation. The kind captions targets people with hearing impairment, whereas descriptions targets people with vision impairment.

Noncompliant code example

<video id="video" controls preload="metadata">
   <source src="resources/myvideo.mp4" type="video/mp4">
   <source src="resources/myvideo.webm" type="video/webm">
</video>

Compliant solution

<video id="video" controls preload="metadata">
   <source src="resources/myvideo.mp4" type="video/mp4">
   <source src="resources/myvideo.webm" type="video/webm">
   <track label="English" kind="captions" srclang="en" src="resources/myvideo-en.vtt" default>
   <track label="Deutsch" kind="captions" srclang="de" src="resources/myvideo-de.vtt">
   <track label="Español" kind="captions" srclang="es" src="resources/myvideo-es.vtt">
</video>

Available In:

Catch issues on the fly,
in your IDE

Detect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

Analyze code in your
on-premise CI

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Sonar helps developers write Clean Code.
Privacy Policy | Cookie Policy

In-IDE

SaaS

Self-Hosted